-
Notifications
You must be signed in to change notification settings - Fork 106
fix(card): add wrapper to img #2578
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
PatternFly-Next preview: https://patternfly-next-pr-2578.surge.sh |
mattnolting
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM @mcoker wdyt?
|
@christiemolloy I dig it, I think this makes the most sense. Though I wonder if we should be more generic in the element name in case someone wants to put some text or text+icon instead. We could call it |
|
I agree with using a less specific name. Also added class to the docs @mcoker |
| <div class="pf-c-card__image{{#if card-image--modifier}} {{card-image--modifier}}{{/if}}" | ||
| {{#if card-image--attribute}} | ||
| {{{card-image--attribute}}} | ||
| <div class="pf-c-card__main{{#if card-main--modifier}} {{card-main--modifier}}{{/if}}" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can we call it __head-main instead, since it should only exist in __head? I think we should reserve __main in case we want to add that to the root of the card.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah +1
mcoker
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nice work! 🥇
|
🎉 This PR is included in version 2.50.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
closes #2562
There may be a few solutions to this problem, I went with the solution of wrapping the image in its own container, because we don't know how the user will give it height/width. So even if width is added to the image in the html or the svg, it will still size proportionally down. But interested to hear what you guys think @mcoker @mattnolting